Relationship Identification Based on Email Traffic

ABSTRACT

A method comprises identifying one or more relationships between a target individual and one or more persons based at least in part on a plurality of emails. The plurality of emails comprise one or more outbound emails, which may comprise emails sent to the target individual from the one or more persons. The plurality of emails further comprise one or more inbound emails, which may comprise emails sent from the target individual to the one or more persons. The method further comprises, for each of the one or more relationships, calculating an amount of outbound emails and an amount of inbound emails. The method further comprises assigning a classification to each of the one or more relationships based at least in part on the amount of outbound emails and the amount of inbound emails. The method further comprises sorting the one or more relationships based at least in part on the classification assigned to each of the one or more relationships. The method may further comprise storing information regarding the sorted relationships.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 61/247,441, entitled “RELATIONSHIP IDENTIFICATION BASED ONEMAIL TRAFFIC” which was filed on Sep. 30, 2009. U.S. Provisional PatentApplication Ser. No. 61/247,441 is hereby incorporated by reference.

TECHNICAL FIELD OF THE DISCLOSURE

This disclosure relates in general to email management systems and, moreparticularly, to relationship identification based on email traffic.

BACKGROUND

As organizations become more complex and diversified, maintaining andorganizing outside business contacts becomes increasingly difficult. Onepart of an organization may not be aware of existing or ongoingrelationships developed or maintained in other parts of an organization.As a result, business relationships with persons or entities outside theorganization may stagnate. Additionally, a person outside anorganization may be contacted by more than one person inside theorganization, which may have negative repercussions for the businessrelationship. As organizations grow, traditional computer and emailsystems are unable to effectively use email traffic data to identify,organize, and leverage business relationships.

SUMMARY

In accordance with the present disclosure, the disadvantages andproblems associated with systems and methods of analyzing email traffichave been substantially reduced or eliminated.

In some embodiments, a method comprises receiving a plurality of emails.Each of the plurality of emails comprises message information and headerinformation. The header information comprises subject information andone or more email addresses. The method further comprises generatingfiltered email data comprising email addresses by at least filteringmessage information and subject information from each of the pluralityof emails. The method further comprises correlating sender informationand recipient information in the filtered email data, the correlationbased at least in part on the one or more email addresses. The methodfurther comprises storing in memory one or more email addresses from thefiltered email data.

In other embodiments, a method comprises receiving, by a processor, aquery comprising at least one name of a target individual. The methodfurther comprises determining, by the processor, a plurality of emailaddresses. Each of the determined email addresses has a respectiveprefix based at least in part upon the at least one name of the targetindividual, and the determination is based at least in part uponstatistical data regarding common syntaxes for email addresses. Themethod further comprises determining email traffic based at least inpart upon the determined email addresses. The method further comprisesdetermining, by the processor, one or more relationships of the targetindividual based at least in part upon the determined email traffic.

In yet other embodiments, a method comprises identifying one or morerelationships between a target individual and one or more persons basedat least in part on a plurality of emails. The plurality of emailscomprise one or more outbound emails, which may comprise emails sent tothe target individual from the one or more persons. The plurality ofemails further comprise one or more inbound emails, which may compriseemails sent from the target individual to the one or more persons. Themethod further comprises, for each of the one or more relationships,calculating an amount of outbound emails and an amount of inboundemails. The method further comprises assigning a classification to eachof the one or more relationships based at least in part on the amount ofoutbound emails and the amount of inbound emails. The method furthercomprises sorting the one or more relationships based at least in parton the classification assigned to each of the one or more relationships.The method may further comprise storing information regarding the sortedrelationships.

In yet other embodiments, a method comprises receiving one or moresearch requests from one or more users, each search request comprising arequest for relationship information that is determined using emaildata, and each search request including at least one of a first name, alast name, and a company name of a target individual. The method furthercomprises storing search information associated with the one or moresearch requests. The search information comprises a plurality of fieldsincluding a user identification associated with each of the one or moreusers, a name of the one or more users, a type of search requestreceived, a name of the target individual, an email address associatedwith the target individual, and a time at which the search request isreceived. The method may further comprise generating an audit reportbased at least in part on the stored search information, wherein theaudit report comprises at least one of the plurality of fields. Themethod further comprises storing the audit report.

The present disclosure provides several important technical advantages.One advantage is that a computer system may provide an intelligentdisplay of relationship information based on email traffic to or from anenterprise. Another advantage is that the system may allow for theintelligent collection, filtration, and/or correlation of emails sent toor from an enterprise. If a user desires to identify a network ofbusiness relationships for a target individual external to theenterprise, the system may allow the user to input informationassociated with the target individual such as, for example, a firstname, a last name, a middle initial, a company name, and/or a companydomain. The system may then generate a list of possible email addressesfor the target individual. Using data regarding email traffic, thesystem may identify and display relationships between one or moreindividuals and a target individual that may be external to theenterprise. The list may be prioritized based on the strength of eachrelationship. Thus, without knowing a particular target individual'semail address, the system may allow a user to discover information aboutany existing relationships between one or more individuals and a targetindividual.

Other technical advantages of the present disclosure will be readilyapparent to one skilled in the art from the following figures,descriptions, and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some, or none ofthe enumerated advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description, taken inconjunction with the accompanying drawings, in which:

FIG. 1 illustrates a system for analyzing email traffic to identifybusiness relationships, according to certain embodiments;

FIG. 2 illustrates an email analyzer from the system illustrated in FIG.1, according to certain embodiments;

FIG. 3 illustrates an example Graphical User Interface (“GUI”) thatassists a user in formulating a query for information regarding a targetindividual, according to certain embodiments;

FIG. 4 illustrates a table comprising example permutations of emailaddresses generated by an email analyzer, according to certainembodiments;

FIG. 5 illustrates an example GUI displaying the results of a query,according to certain embodiments;

FIG. 6 illustrates an example GUI showing an audit report generated byan email analyzer, according to certain embodiments; and

FIG. 7 illustrates a flow diagram for analyzing email traffic toidentify business relationships, according to certain embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 10 for analyzing email traffic to identifybusiness relationships, according to certain embodiments. System 10 maygenerally receive, filter, and correlate email data 25 to identify anetwork of business relationships of a target individual 80. System 10may generate likely email addresses of target individual 80 based atleast in part on a first name, last name, middle name (or initialthereof) and a company name, domain associated with a company, and/orother information associated with target individual 80. In someembodiments, system 10 may prioritize the identified businessrelationships based on certain characteristics such as, for example, thevolume of email traffic sent to and/or from target individual 80. System10 may audit searches performed by users and may track and display audittrails containing various data attributes. System 10 may include anemail analyzer 20, email server 30, email repository 40, one or moreexternal data sources 50, one or more networks 60, and one or moreclients 70.

Email analyzer 20 may receive, process, and/or analyze email data 25sent to or from enterprise 15. In particular embodiments, email data 25may include one or more emails sent to or from individuals in enterprise15. For each email, email data may comprise header information, messagetext, metadata (e.g., time sent, date modified, etc.), and/or anysuitable information. Email data 25 may include entire emails or onlyportions of emails. In some embodiments, the message body and/or subjectinformation (e.g., the subject line) of an email may be filtered fromemail data 25. In some embodiments, email analyzer 20 may process emaildata 25 to generate correlated and filtered data that may be efficientlysearched and/or analyzed.

In some embodiments, email analyzer 20 may generate, based on receivedsearch terms, a list of potential email addresses for target individual80. Target individual 80 may be any person, group of persons, and/orentity within or without enterprise 15. In some embodiments, targetindividual 80 is external to and/or not affiliated with enterprise 15.Email analyzer 20 may allow a user to identify a network of businessrelationships that target individual 80 has with other people orentities. In particular embodiments, a user may input into system 10 thefirst name, last name, and/or middle name (or initial thereof) and/or acompany name, a domain associated with a company, and/or other suitableinformation associated with target individual 80. Using rules based onstatistical data, email analyzer 20 may generate a list of potentialemail addresses associated with target individual 80. Email analyzer 20may then identify and intelligently display possible relationships thattarget individual 80 has with persons in enterprise 15 and personsoutside of, or not belonging to, enterprise 15. For example, based onemail traffic to and/or from the potential email addresses for targetindividual 80, email analyzer 20 may group, sort, and/or classifyrelationships of target individual 80. Email analyzer 20 may thenidentify and intelligently display possible relationships that targetindividual 80 has with persons inside and/or outside of enterprise 15.For example, based on email traffic to and from the potential emailaddresses for target individual 80, email analyzer 20 may group, sort,and/or classify relationships of target individual 80.

In some embodiments, email analyzer 20 may track and display an audittrail for each search conducted by a user of system 10. The audit trailfor a particular search may comprise various data attributes such as,for example, the name of the user performing the search, the type ofsearch (e.g., company name, individual name, exact email address, etc.),the company and/or individual name in the search, the time of thesearch, and/or any suitable information. Email analyzer 20 may beconfigured to generate periodic audit reports based on predeterminedthresholds of usage activity. Email analyzer 20 may also generate auditreports based on a request from a user of system 10.

Email analyzer 20 may be any suitable computing device comprising aprocessor and a memory. For example, email analyzer 20 may comprise oneor more workstations, laptops, blade servers, server farms, and/or standalone servers. Although shown in FIG. 1 as comprising a singlecomponent, email analyzer 20 may, in some embodiments, representfunctionality provided by several separate physical components. In someembodiments, email analyzer 20 may represent software operating on oneor more servers. Although FIG. 1 illustrates, for purposes of example, asingle email analyzer 20, particular embodiments of system 10 mayinclude any appropriate number of email analyzers 20 arranged in anysuitable configuration. In embodiments that include multiple emailanalyzers 20, each respective email analyzer 20 may be operable tocommunicate, directly or indirectly, with one or more other emailanalyzers 20 over network 60.

As shown in FIG. 1, email analyzer 20 may be maintained and/or operatedby enterprise 15. Enterprise 15 may represent any organization,business, association, group, and/or entity organized for any suitablepurpose(s), such as, for example, commercial, educational, and/ornon-profit purpose(s). Although FIG. 1 illustrates enterprise 15comprising a single location, enterprise 15 may include any number oflocations, and system 10 may operate across multiple locations or in asingle location.

Enterprise 15 may comprise one or more email servers 30. Email server 30may send and/or receive emails generated by users within enterprise 15and may receive emails from persons outside enterprise 15 sent to userswithin enterprise 15. In particular embodiments, email server 30 mayrepresent a Microsoft Exchange email server, a Unix-based server runninga sendmail or Simple Mail Transfer Protocol application, and/or otherappropriate type of server. Additionally, or alternatively, email server30 may maintain a list of organizational contacts for each user or groupof users of system 10. For example, in particular embodiments, emailserver 30 may include contact manager software (e.g., Microsoft Outlook)that organizes and/or stores contact information for persons within andwithout enterprise 15. Email server 30 may be communicatively coupled,directly or indirectly, to email repository 40. Email server 30 maystore, archive, and/or otherwise retain copies of emails on emailrepository 40.

Email repository 40 may store emails sent, received, and/or processed byemail server 30. In particular embodiments, email repository 40 mayrepresent a database connected to email server 30 and/or a databaseprocess executing on email server 30. Additionally or alternatively,email repository 40 may be capable of storing, archiving, and/orotherwise maintaining a database of organizational contacts. Asdiscussed above, email server 30 may include contact manager softwarethat organizes and/or stores contact information. Email repository 40may store a database of contact information utilized by contact managersoftware. Email repository 40 may be communicatively coupled, directlyor indirectly, to email server 30. In particular embodiments, emailrepository 40 may communicate with email server 30 over network 60.

Email repository 40 may be any suitable computing device comprising aprocessor and a memory. For example, email repository 40 may compriseone or more workstations, laptops, blade servers, server farms, and/orstand alone servers. Although shown as comprising a single component,email repository 40 may, in some embodiments, represent functionalityprovided by several separate physical components. In particularembodiments, email repository 40 may represent software operating on oneor more servers. Although FIG. 1 illustrates a single email repository40, particular embodiments may include any appropriate number of emailrepositories 40.

As noted above, system 10 may comprise one or more external data sources50. External data source 50 may represent one or more sources ofinformation that facilitate the operation of system 10. In particularembodiments, external data source 50 may represent one or more dataservers external to enterprise 15 that may be communicatively coupled toone or more components of system 10. In particular embodiments, externaldata source 50 may communicate, directly or indirectly, with emailanalyzer 20 over network 60. For example, external data source 50 mayinclude a data feed from a market center, trading exchange, financialinformation database, contact information database, and/or an electronicdirectory maintained by a third party (e.g., Hoover's, BoardEx, BigDough, Bloomberg, Ipreo, and/or Salesforce.com). Access to, or receivinginformation from, one or more external data sources 50 may provide emailanalyzer 20 with information regarding an external organization'sexecutives, domain name, address, key officers and/or employees, and/orany suitable information pertaining to individuals and/or organizationsoutside of enterprise 15.

External data source 50 may communicate with system 10 via network 60.Network 60 may represent any form of communication network supportingcircuit-switched, packet-based, and/or any other suitable type ofcommunications. Network 60 may additionally include any other componentsof system 10 capable of transmitting and/or receiving information over acommunication network, including email analyzer 20, email server 30,email repository 40, and/or clients 70. Although shown in FIG. 1 as asingle element, network 60 may represent one or more separate networks(including all or parts of various different networks) that areseparated and serve different respective email analyzers 20 and/or emailrepositories 40. Network 60 may include routers, hubs, switches,firewalls, content switches, gateways, call controllers, and/or anyother suitable components in any suitable form or arrangement. Network60 may include, in whole or in part, one or more secured and/orencrypted Virtual Private Networks (VPNs) operable to couple one or morenetwork elements together by operating or communicating over elements ofa public or external communication network. In general, network 60 maycomprise any combination of public or private communication equipmentsuch as elements of the public switched telephone network (PSTN), aglobal computer network such as the Internet, a local area network(LAN), a wide area network (WAN), or other appropriate communicationequipment.

Users may interact with system 10 using clients 70. Client 70 may sendand/or receive emails and may generate one or more queries 75 for targetindividuals 80. Query 75 may represent an electronic request forrelationship information pertaining to a particular target individual80. A user may input query 75 into client 70, which may send query 75 toemail analyzer 20. Query 75 may include one or more characteristics oftarget individual 80. For example, a user may generate query 75 fortarget individual 80 by inputting into client 70 at least a portion ofthe name, email address, and/or company name of target individual 80.Client 70 may display the results of query 75 on a display device.

Clients 70 may represent general or special-purpose computers operatingsoftware applications capable of performing the described operations.For example, clients 70 may include, but are not limited to, laptopcomputers, desktop computers, and/or portable data assistants (PDAs).Additionally, in particular embodiments, client 70 may include one ormore processors operable to execute computer logic and/or softwareencoded on tangible media that perform the described functionality.Client 70 may include one or more input devices such as a keyboard,trackball, mouse, and/or one or more Graphical User Interfaces (GUIs)through which a user may interact with the logic executing on theprocessor of client 70. Client 70 may include any appropriatecombination of hardware, software, and/or encoded logic suitable toperform the described functionality. Clients 70 may be communicativelycoupled with email analyzer 20 and/or email server 30, directly orindirectly, over network 60. Although FIG. 1 illustrates, for purposesof example, a particular number and type of clients 70, alternativeembodiments of system 10 may include any appropriate number and type ofclients 70.

In operation, system 10 may use email data 25 to identify and leveragerelationships that target individual 80 has with people within and/orwithout enterprise 15. In some embodiments, email analyzer 20 in system10 may receive one or more queries 75 from users and may generateprioritized relationship data 85 based on email traffic between one ormore persons and one or more target individuals 80. In some embodiments,a user at client 70 generates query 75 by inputting relevant parametersinto a GUI associated with client 75 such as, for example, a first name,last name, and/or middle name (or initial thereof) and/or a companyname, a domain associated with a company, and/or other suitableinformation associated with target individual 80. Client 70 may transmitquery 75 over network 60 to email analyzer 20.

At appropriate points during operation, email analyzer 20 may receiveemail data 25 from email server 30 and/or email repository 40. Emailanalyzer 20 may filter and/or correlate email data 25 to generaterelationship data 85 based on email traffic. Email analyzer 20 may usefiltered and/or correlated email data 25 to deteiinine a volume of emailtraffic sent to and/or from target individual 80. Based on the volume ofemail traffic, email analyzer 20 may identify and classify relationshipsbetween one or more persons and target individual 80. For example, emailanalyzer 20 may determine that ten or more emails have been sent and/orreceived between Person A in enterprise 15 and target individual 80.Based on this volume of email traffic, email analyzer 20 may, forexample, classify the relationship between Person A and targetindividual 80 as strong. As another example, email analyzer 20 maydetermine that between five and ten emails have been sent and/orreceived between Person B in enterprise 15 and target individual 80.Based on this volume of email traffic, email analyzer 20 may, forexample, classify the relationship between Person B and targetindividual 80 as moderate.

After classifying one or more relationships of target individual 80specified in query 75, email analyzer 20 may transmit relationship data85 to clients 70. In particular embodiments, relationship data 85 may betransmitted over network 60. Relationship data 85 may include datarepresenting one or more attributes of a relationship. For example,relationship data 85 may include the name of a person with whom targetindividual 80 corresponds via email, the source of the person's contactinformation (e.g., email traffic, contact manager database, and/or otherdatabase), and an indicator of the strength of the relationship (e.g.“Knows Well,” “Acquaintance,” etc.). In some embodiments, relationshipdata 85 may be displayed on a GUI by client 70 in a prioritized mannerbased on the strength of the relationship.

One or more embodiments of system 10 may provide important technicaladvantages. For example, system 10 may provide an intelligent display ofrelationship data 85 based on email traffic to or from enterprise 15. Insome embodiments, system 10 facilitates the intelligent collection,filtration, and/or correlation of emails sent to or from enterprise 15.If a user desires to identify a network of business relationships fortarget individual 80 inside or outside of enterprise 15, system 10 mayallow the user to input information associated with the targetindividual 80, such as a first name, a last name, a middle name (orinitial thereof), a company name, and/or a domain associated with acompany. System 10 may then generate a list of possible email addressesfor target individual 80. Using email data 25, system 10 may identifyand display relationships of target individual 80. The relationships maybe prioritized based on the strength of each relationship. Thus, withoutknowing the actual email address of target individual 80, system 10 mayallow a user to discover information about any existing relationshipsbetween individuals inside or outside an enterprise and targetindividual 80. Particular embodiments of system 10 may provide some,none, or all of the foregoing advantages.

FIG. 2 illustrates email analyzer 20 in system 10, according to certainembodiments. Email analyzer 20 may generally receive, process, sort,analyze, and/or intelligently display information associated with emailssent to or from enterprise 15. In particular embodiments, email analyzer20 may audit users of system 10 and/or may audit queries 75 associatedwith the use of email analyzer 20. Email analyzer 20 may include aprocessor 210, memory 220, interface module 230, preprocessing module240, derivation module 250, classification module 260, and auditingmodule 270.

Processor 210 may represent and/or include any form of processingcomponent, including general purpose computers, dedicatedmicroprocessors, or other processing devices capable of processingelectronic information. Examples of processor 210 include digital signalprocessors (DSPs), application-specific integrated circuits (ASICs),field-programmable gate arrays (FPGAs), and any other suitable specificor general purpose processors. Although FIG. 2 illustrates a singleprocessor 210 in email analyzer 20, email analyzer 20 may include anysuitable number of processors 210. In embodiments of system 10 in whichemail analyzer 20 represents software executing on other components ofsystem 10, processor 210 may represent a processor utilized inperforming operations associated with the particular component on whichemail analyzer 20 is operating.

Processor 210 may be communicatively coupled to memory 220. Memory 220may store processor instructions, queries 75, results of queries 75,email data 25, audit results, and/or any suitable information. Memory220 may comprise any collection and arrangement of volatile and/ornon-volatile components suitable for storing data. For example, memory220 may comprise random access memory (RAM) devices, read only memory(ROM) devices, magnetic storage devices, optical storage devices, and/orany other suitable data storage devices. In particular embodiments,memory 220 may represent, in part, computer-readable storage media onwhich computer instructions and/or logic are encoded. In suchembodiments, some or all the described functionality of email analyzer20 may be provided by processor 210 executing the instructions encodedon the described media. Although shown in FIG. 2 as a single component,memory 220 may represent any number of memory components within, localto, and/or accessible by email analyzer 20. Although shown in FIG. 2 asbeing located internal to email analyzer 20, memory 220 may representstorage components remote from email analyzer 20 such as, for example,components of a Network Attached Storage (NAS), Storage Area Network(SAN), or any other type of remote storage system.

Processor 210 may be communicatively coupled to one or more interfacemodules 230 in email analyzer 20. Interface module 230 may facilitatecommunication between email analyzer 20, email server 30, emailrepository 40, clients 70, and/or other components of system 10. Forexample, email analyzer 20 may receive query 75 from client 70 throughinterface module 230. Through interface module 230, email analyzer 20may receive email data 25 from email server 30 and/or email repository40. In particular embodiments, interface module 230 may include orrepresent one or more interface cards suitable for communication overnetwork 60. Although FIG. 2 illustrates a single interface module 230 inemail analyzer 20, email analyzer 20 may include any suitable number ofinterface modules 230.

Email analyzer 20 may comprise one or more preprocessing modules 240.Preprocessing module 240 may generally receive, filter, and/or correlateraw email data 25 from email repository 40. Processor 210 may use thefiltered and/or correlated email data 25 output by preprocessing module240 to determine results of queries 75 from users. Preprocessing module240 may receive email data 25 from email repository 40 in real-timeand/or in periodic batches. For example, preprocessing module 240 mayreceive and process email data 25 once every month, once every week,and/or according to any appropriate schedule. Once raw email data 25 isreceived, whether in real-time or in batches, preprocessing module 240may process the raw email data 25 to generate correlated and/or filteredemail data 25 that may be efficiently searched. For example, inparticular embodiments, preprocessing module 240 may isolate headerinformation from emails in raw email data 25. Preprocessing module 240may filter subject information (e.g., the subject line of an email)and/or message text from the emails in the raw email data 25. That is,preprocessing module 240 may isolate message text from relevant emailsand store and/or process all or only header information. Preprocessingmodule 240 may, additionally or alternatively, correlate redundantinstances of emails from email data 25 (e.g., redundant emails mayresult from distribution lists and/or from emails sent to multiplerecipients). Some and/or all of the functions of preprocessing module240 described above may be performed by email server 30.

In some embodiments, preprocessing module 240 may correlate emails inemail data 25 from email repository 40 based on senders and recipients.For example, preprocessing module 240 may group together an email sentfrom Person A to Person B and a reply from Person B to Person A.Preprocessing module 240 may capture email addresses from the headerinformation associated with emails. For example, preprocessing module240 may identify and store email addresses from the “To” field, the“From” field, the “Cc” field, and/or the “Bcc” field of emails.Preprocessing module 240 may, additionally or alternatively, linkinformation in email data 25 to electronic directories. For example,preprocessing module 240 may identify an email address in the headerinformation of email data 25 and may retrieve additional informationcorresponding to the email address (e.g., a name, telephone number,address, etc.) from one or more additional data sources such as, forexample, a contacts database, a human resources database, etc. Inparticular embodiments, preprocessing module 240 may receive informationfrom one or more external data sources 50 and may determine whetheremails sent to or from individuals or organizations identified byexternal data sources 50 correspond to emails in email data 25 fromemail server 30 or email repository 40.

Email analyzer 20 may comprise one or more derivation modules 250.Derivation module 250 may generate, based on received query terms, alist of potential email addresses for target individual 80. Thus, a userof system 10, without knowing the actual email address of targetindividual 80, may input a first name, last name, middle name (orinitial thereof), company name, and/or domain associated with a companyof target individual 80, and derivation module 250 may generate a listof potential email addresses. Derivation module 250 may generate thelist of possible email addresses using rules based on statistical dataregarding common structures and syntax for prefixes and/or domains ofemail addresses. Using statistical data may allow derivation module 250to generate likely email addresses of target individual 80 instead ofmerely random permutations of character data. Each possible emailaddress may be derived from different permutations of the initials, thefirst name, the last name, the middle name, the company name, thecompany domain, and/or one or more other characters associated withtarget individual 80. For example, a user of system 10 may wish toidentify persons who know John Q. Public of Whiteacre Company. The usermay formulate a query by inputting “John Q. Public” as the name and“Whiteacre Company” as the company of target individual 80. Derivationmodule 250 may then use statistical data to generate a list of potentialemail addresses (e.g., j.public@whiteacre.com, j.q.public@whiteacre.com,j-public@whiteacre.com, etc.). In some embodiments, email analyzer 20may filter one or more numeric characters from prefixes of emailaddresses in conjunction with searching for relationships and/oranalyzing email traffic.

Derivation module 250 may rank the potential email addresses based atleast in part on the frequency at which the associated prefix and/ordomain structure (e.g., firstinitial.lastname,firstname.middleinitial.lastname, etc.) appear in archived email data25. Based on the potential email addresses generated by derivationmodule 250, email analyzer 20 may search email data 25 output bypreprocessor module 240 to identify relationships between targetindividual 80 and other people. The relationships may be identifiedbased on email traffic between the potential email addresses generatedby derivation module 250 and other email addresses.

Email analyzer 20 may comprise one or more classification modules 260.Classification module 260 may identify and intelligently displayinformation regarding relationships between individuals within orwithout enterprise 15. As discussed above, email analyzer 20 mayidentify relationships based on email traffic between potential emailaddresses of target individual 80 (as generated by derivation module250) and other email addresses. Classification module 260 may thenintelligently sort the relationships according to the type of eachrelationship. For example, if contact classification module 260 findsten or more emails from target individual 80 to Person A and only twoemails from Person A to target individual 80, then classification module260 may classify the relationship with Person A as “High Inbound/LowOutbound.” In another example, if classification module 260 finds fiveor fewer emails from target individual 80 to Person A and five emailsfrom Person A to target individual 80, classification module 260 mayclassify the relationship as “Moderate Inbound/Moderate Outbound.” Thevolume of emails corresponding to each particular threshold and thenumber of thresholds used may be configurable according to the needs ofthe user and/or enterprise 15 and the overall capabilities of system 10.In some embodiments, classification module 260 may classify therelationship for each person with whom target individual 80 corresponds.Classification module 260 may present an intelligent display that sortsthe relationships according to type. For example, in particularembodiments, relationships classified as “High Inbound/High Outbound”may be displayed first, while relationships classified as “LowInbound/Low Outbound” may be displayed last. The particular types ofrelationships displayed, as well as the order in which they aredisplayed, may be configurable by a user of system 10.

In particular embodiments, classification module 260 may classifyrelationships based, at least in part, on factors other than emailtraffic. For example, the classification may be based, at least in part,on email directories and/or contact lists. Classification module 260 maybe capable of receiving contact information from email server 30 and/oremail repository 40. For example, email server 30 and/or emailrepository 40 may store or maintain a contacts database using contactmanagement software such as, for example, Microsoft Outlook and/or LotusNotes. In particular embodiments, each user in system 10 maintains arespective directory of contacts. A user's directory of contacts may bestored on that user's computer and/or in memory in email server 30and/or email repository 40. A particular user may use contact managementsoftware to designate certain contacts in the contacts database as beingstrong or weak. For example, particular contacts may be marked as “KnowsWell,” as “Knows a Little,” as “Acquaintance,” etc. Based on thestrength of the relationship, classification module 260 may give ahigher or lower priority to a particular relationship in the display ofrelationship data 85. Stronger relationships may be listed above weakerrelationships.

In some embodiments, classification module 260 may identify andde-prioritize spam emails and/or may mask certain data (e.g., employeenames, employee identification numbers, etc.) depending on the securityclearance of the user. The amount and/or type of information presentedin a display of relationship data 85 may be configurable based on thesecurity clearance of the user that generated the particular query 75.For example, user names, identifying information, and/or email addressesmay be hidden or revealed based on the role of the user withinenterprise 15. Thus, classification module 260 may provide anintelligent display of relationships based on email traffic and/or otherinformation sources.

Email analyzer 20 may comprise one or more auditing modules 270.Auditing module 270 may generally determine, maintain, and/or display anaudit trail for each query 75 conducted by a user of system 10. Theaudit trail for a particular query 75 may comprise various dataattributes such as, for example, the name of the user performing thesearch, the type of search (e.g., company name, individual name, emailaddress, etc.), the company and/or individual name in query 75, the timeof query 75, etc. In particular embodiments, if the volume and/orfrequency of queries 75 by a particular user of system 10 exceeds aconfigurable threshold, auditing module 270 may notify an administratoror other operator of system 10. In particular embodiments, auditingmodule 270 may send an email that includes a report regarding the searchhistory of the particular user. Additionally or alternatively, auditingmodule 270 may provide a real-time audit log of queries 75 generated byusers of system 10 and/or executed by email analyzer 20. Thus, auditingcapabilities provided by auditing module 270 may allow system 10 todetect and prevent misuse of particular features of system 10.

Each of processor 210, memory 220, interface module 230, preprocessingmodule 240, derivation module 250, classification module 260, andauditing module 270 may represent any appropriate combination ofhardware and/or software suitable to perform the described functions.Elements of email analyzer 20 may include logic encoded on tangible,computer-readable media and executed on processor 210 and/or othercomputer hardware suitable to provide the described functions of emailanalyzer 20. Additionally, any two or more of the described modules mayrepresent or include common components.

FIG. 3 illustrates an example Graphical User Interface (“GUI”) 300 thatassists a user in formulating query 75 for information regarding targetindividual 80, according to certain embodiments. Client 70 may displayGUI 300 to a user. By interacting with GUI 300, the user may generatequeries 75 for target individuals 80 and may view information regardingrelationships of target individual 80. GUI 300 may include input boxes302 a, 302 b, and 302 c that allow the user to formulate query 75. Inputbox 302 a may receive user input for a first name of target individual80. Input box 302 b may receiver user input for a last name of targetindividual 80. Input box 302 c may receive user input for a company nameand/or domain associated with a company of target individual 80. Inparticular embodiments, a user may formulate query 75 by inputtinginformation into one or more of input boxes 302. In some embodiments,GUI 300 may include additional input boxes 302 whereby a user may inputadditional information including, for example, an email address, a workaddress, a telephone number, etc.

In some embodiments, GUI 300 includes a search type selector 304 thatallows a user to designate the type of query to be performed. Searchtype selector 304 may include options for “Enterprise Only,” “EmailRelationships Only,” and “All Relationships.” Selecting “EnterpriseOnly” may enable queries 75 for contacts within a contacts databasemaintain by system 10 and/or external information sources 50. Selecting“Email Relationships Only” may enable queries for relationships betweentarget individual 80 and persons in enterprise 15 (e.g., by searchingemail data 25 for emails between target individual 80 and a person inenterprise 15). Selecting “All Relationships” may enable searching forrelationships between target individual 80 and persons in enterprise 15(e.g., by searching a contacts database, external information sources50, and/or email data 25 for emails associated with target individual80).

In some embodiments, GUI 300 comprises a sort box 306 that allows a userto select a preference for the order in which results are displayed. Forexample, a user may wish to see results of a particular query 75 in theorder of last name, first name, organization, etc. Thus, sort box 306may be a drop-down box that contains one or more of these or othersorting options.

In some embodiments, GUI 300 comprises a search results box 308 thatdisplays the results of query 75 for target individual 80. For example,as shown in FIG. 3, a user has input query 75 for target individual 80named “John Doe.” The user has selected “All Relationships” in searchtype selector 304. As discussed above, email analyzer 20 may generate alist of potential email addresses for target individual 80. Emailanalyzer 20 may then search email data 25 received from email server 30and/or email repository 40 for one or more of the potential emailaddresses. As shown in the illustrated example, search results box 308may display one or more potential matching names for the particulartarget individual 80. Once displayed, a user may select a particularname to obtain more information about target individual 80.

In some embodiments, GUI 300 may comprise a display option box 310 thatmay filter names displayed in search results box 308. In particularembodiments, by selecting various options, a user may be able to displayonly names found in a contacts database, found through email data 25,and/or found through any other relevant source. Conversely, byunselecting one or more options, a user may be able to hide names foundin a contacts database, through email data 25, and/or through any otherrelevant source.

FIG. 4 illustrates a table 400 comprising example email permutationsgenerated by email analyzer 20, according to certain embodiments. Asdiscussed above, email analyzer 20 may generate, based on received queryterms, a list of potential email addresses for target individual 80.Thus, email analyzer 20 may allow a user to search email data 25 forrelationships with target individual 80 without necessarily knowing theactual email address or addresses of target individual 80. Accordingly,a user of system 10, without knowing the actual email address of aperson inside or outside of enterprise 15, may input the person's firstname, last name, middle name (or initial), company name, and/or companydomain. Email analyzer 20 may then generate a list of likely emailaddresses. In the illustrated example, email analyzer 20 received query75 for target individual 80 named “John Q. Public” who works at“Whiteacre Company.” Email analyzer 20 may generate likely emailaddresses based on one or more of (in whole or in part) a first name, amiddle name, a last name, a company name, and/or one or more additionalcharacters. Email analyzer 20 may use all or part of the first name,middle name, and/or last name to generate one or more likely emailprefixes. Email analyzer 20 may use all or part of the company name togenerate one or more likely email domains. The term prefix may refer tothe portion of an email address before the “@” symbol, and the termdomain may refer to the portion of an email address after the “@”symbol. Email analyzer 20 may determine various prefixes and domainsbased at least in part on statistical data regarding common syntaxes andstructures of email addresses. Although FIG. 4 illustrates for purposesof example a particular list of possible email addresses, numerous otherpossible addresses may be generated by email analyzer 20.

FIG. 5 illustrates an example GUI 500 displaying the results of query75, according to certain embodiments. GUI 500 may comprise aclassification matrix 510, one or more priority rules 520, and at leastone results table 530. Matrix 510 may visually depict logic forclassifying the strength of relationships associated with targetindividual 80. In particular, matrix 510 may depict a sorting algorithmfor classifying email traffic sent to and/or received from targetindividual 80. For example, matrix 510 may comprise rows that representthe volume of outbound email sent from Person A to Person B. Person Aand/or Person B may be within or without enterprise 15. The columns inmatrix 510 may represent the volume of inbound email sent from Person Bto Person A. For each of the vertical and horizontal sets of data,“None” may indicate that no email was sent or received. “L” may indicatethat a relatively low amount of emails were sent or received. Thus, “L”may represent an amount less than first threshold number of emails sentand/or received between Person A and Person B. “M” may indicate that amoderate amount of emails were sent or received. “M” may represent anamount between a first threshold and a second threshold. “H” mayindicate that a high volume of emails were sent or received. “H” mayrepresent an amount equal to or greater than the second threshold. Eachof the respective first and second thresholds may be configurable basedon the total number of emails received, the strength of the businessrelationships, and/or any other relevant considerations, factors, and/orvariables. An intersection of “H” inbound emails and “H” outbound emailsmay indicate a strong (or “A”) relationship between Person A and PersonB. In the example shown, any combination of “H-H” or “H-M” may bedesignated as an “A” relationship. Similarly, “B” relationships mayinclude any combination of “L-H” and/or “L-M.” Any combination includinga designation of “None” may indicate that there is no meaningfulrelationship (i.e., a “C” relationship). Based at least in part on theparticular designation (“A,” “B,” or “C,”), email analyzer 20 mayprioritize relationships when presenting a list of relationships to auser.

In some embodiments, priority rules 520 may define a particularpreference order for sorting and/or displaying relationships. Forexample, based at least in part on priority rules 520, email analyzer 20may sort and/or display relationships in a particular order, includingbut not limited to: (1) relationships between board members ofenterprise 15 and an outside organization; (2) relationships where atleast one correspondent is designated in a contacts database as “KnowWell”; (3) email traffic in which the relationship betweencorrespondents is designated as an “A” relationship as described above;(4) email traffic in which the relationship between correspondents isdesignated as a “B” relationship as described above; (5) relationshipswhere at least one correspondent is designated in a Microsoft Outlookcontacts database as “Know A Little”; and (6) email traffic in which therelationship between correspondents is designated as a “C” relationship.The particular order specified by priority rules 520 may be configurablein accordance with the wishes or needs of a particular user of system10.

Results table 530 may display one or more relationships identified byemail analyzer 20 in response to query 75 from a user. In theillustrated example, results table 530 displays various relationships oftarget individual 80 named “Jane R. Doe.” Results table 530 mayoptionally display (1) the parties to the relationship (e.g., a personwithin enterprise 15 that has a relationship with target individual 80);(2) the role (e.g., job title) of each party; (3) the volume of emailbetween the two parties (either inbound, outbound, or both); (4) whethertarget individual 80 appears in the contacts database of a party; and/or(5) whether target individual 80 is designated as “Knows Well” or “KnowsA Little” in a contacts database. Results table 530 may display aprioritized list of relationships in accordance with the preferenceorder specified by priority rules 520. Depending on a user's level ofaccess, GUI 500 may display an actual number of emails sent to and/orfrom target individual 80, or GUI 500 may display a general descriptionof the number of emails sent and/or received (e.g., high, medium, orlow).

FIG. 6 illustrates GUI 600 showing an example audit report generated byemail analyzer 20, according to certain embodiments. As discussed above,email analyzer 20 may determine and display an audit trail for queries75 conducted by each user of system 10. An administrator of system 10may request email analyzer 20 to generate an audit trail for one or moreusers. GUI 600 may include at least one table 610 that includes aplurality of fields for each user audited. Table 610 may display one ormore user identifiers, a last name, a first name, a role withinenterprise 15, a region, a number of queries generated by each userduring particular months, and the total number of queries generated by auser during a configurable time period (e.g., over the last year). GUI600 may allow the administrator to select a particular user to requestadditional information relating to a particular audit trail. Aparticular audit trail may comprise various data attributes such as, forexample, the name of the user performing the search, the type of search(e.g., company name, individual name, exact email address, etc.), thecompany and/or individual name in the query 75, the time of the search,and/or any other appropriate attributes. Email analyzer 20 may beconfigured to generate periodic reports based at least in part onpredetermined thresholds of usage activity. Further, as discussed above,an audit report containing one or more tables 610 may be automaticallygenerated and sent to an administrator based on a predeterminedconfiguration. For example, an audit report may be generated and/or sentperiodically (e.g., once every month, once every six months, etc.) ormay be generated upon request by an administrator. In some embodiments,an audit report may be generated and/or sent based on the volume and/orfrequency of queries 75 by a particular user exceeding a configurablethreshold.

FIG. 7 is a flow diagram illustrating an operation in accordance with aparticular embodiment of system 10. In the illustrated example,operation begins at step 700 with email analyzer 20 receiving one ormore emails from email server 30. In particular embodiments, emailanalyzer 20 may receive email data 25 from email server 30 and/or emailrepository 40. Email analyzer 20 may receive email data 25 in real-timeor in periodic batches. For example, email analyzer 20 may receive emaildata 25 once every month, once every week, and/or according to anyappropriate schedule. Email analyzer 20 may be capable of receivingemail data 25 in response to query 75 or command by a user of system 10.

At step 702, email analyzer 20 may process, correlate, and/or filteremails in email data 25. As discussed above, email analyzer 20 mayprocess raw email data 25 to generate correlated and filtered email data25 that may be efficiently searched. For example, email analyzer 20 maycorrelate redundant instances of emails (e.g., redundant emails mayresult from distribution lists or from emails sent to multiplerecipients). Email analyzer 20 may correlate emails based on senders andrecipients. For example, email analyzer 20 may group together an emailsent from Person A to Person B and a reply from Person B to Person A.Email analyzer 20 may group together an email sent from Person A toPerson B and a forwarded email from Person B to Person C. In general,emails may be associated in any appropriate manner suitable tofacilitate efficient searching and/or processing in system 10.

At step 704, email analyzer 20 may isolate message text information fromheader information in email data 25. For example, in particularembodiments, email analyzer 20 may isolate header information in emaildata 25 and filter the message text from the email data 25. That is,email analyzer 20 may strip message text from relevant emails and storeand/or process only header information. In some embodiments, emailanalyzer 20 may filter subject information from the header informationin email data 25. Email analyzer 20 may capture email addresses fromheader information in email data 25. For example, email analyzer 20 mayanalyze header information in email data 25 and store one or more emailaddresses contained in the header information (e.g., email addressescontained in the “To” field, the “From” field, the “Cc” field, or the“Bcc” field). Email analyzer 20 may additionally link data in emails toelectronic directories. As discussed above, in particular embodiments,email analyzer 20 may receive information from one or more external datasources 50 and may determine whether emails sent to or from individualsor organizations identified by external data sources 50 correspond toemail data 25 received from email server 30 or email repository 40. Inparticular embodiments, email analyzer 20 may store the correlated andfiltered email data 25 in a memory associated with email analyzer 20.

At step 706, a user of system 10 may enter one or more query terms. Inparticular embodiments, a user of system 10 may query whether personswithin or without enterprise 15 have relationships with targetindividual 80. Using a GUI at client 70, a user may query system 10 forinformation about target individual 80. By interacting with a GUI, auser of system 10 may be able to generate queries 75 for targetindividuals 80 and receive responses for potential relationships thatmay match the relevant information entered.

At step 708, email analyzer 20 may generate possible email addresses fora given query 75. As discussed above, email analyzer 20 may generate,based on received query terms, a list of potential email addresses fortarget individual 80. In general, email analyzer 20 may allow a user tosearch email data 25 for relationships with target individual 80 withoutnecessarily knowing the exact email address or addresses of targetindividual 80.

At step 710, email analyzer 20 may search one or more databases forinformation matching the queried target individual 80. In particularembodiments, email analyzer 20 may search stored and/or correlated emaildata 25 received in step 704 for email addresses that match one or moreof the email addresses generated in step 708. Additionally, emailanalyzer 20 may search a contacts database for a name, email address,company name, and/or other information that matches target individual 80queried in step 706. Email analyzer, in particular embodiments, maysearch one or more external information sources 50 for a name, emailaddress, company, and/or other information that matches targetindividual 80 queried in step 706.

At step 712, email analyzer 20 displays search results to a user. Asdiscussed above with respect to FIG. 3, email analyzer 20 may displaysearch results for a particular target individual 80 in a search resultsbox in a GUI associated with client 70. Search results may be grouped inorder of relevance and/or in accordance with the particular source fromwhich a particular result was found. For example, email analyzer 20 maysearch for information in one or more databases, including externalinformation sources 50, correlated and/or stored email data 25, and acontacts database. As discussed above, email analyzer 20 may generate alist of potential email addresses for the name and/or organizationentered and may search email information received from email server 30and/or email repository 40 for one or more of the generated emailaddress.

At step 714, email analyzer 20 may display relationship data 85 to auser. In particular embodiments, email analyzer 20 may transmitrelationship data 85 to a particular client 70 to be displayed on a GUI.Relationship information may include information pertaining toindividuals within or without enterprise 15 that have a relationshipwith target individual 80, an indication of the strength of each suchrelationship, information regarding the volume of emails between theperson and target individual 80, and/or the particular database in whichtarget individual 80 was found by email analyzer 20. Email analyzer 20may classify the relationships for each person with whom targetindividual 80 corresponds. For example, if email analyzer 20 finds tenor more emails from target individual 80 to Person A and only two emailsfrom Person A to the target individual, then the relationship withPerson A may be classified as “High Inbound/Low Outbound.” In anotherexample, if there are five or fewer emails from target individual 80 toPerson A and five emails from Person A to the target individual, emailanalyzer 20 may classify the relationship as “Moderate Inbound/ModerateOutbound.”

The volume of emails corresponding to each particular threshold, and thenumber of thresholds use may be configurable according to the needs ofenterprise 15 and the overall capabilities of system 10. Based on therelevant classifications and/or identification of potentialrelationships, email analyzer 20 may present an intelligent display thatsorts the relationships according to type. For example, in particularembodiments, relationships classified as “High Inbound/High Outbound”may be displayed first, while relationships classified as “LowInbound/Low Outbound” may be displayed last. Additionally, theparticular types of relationships displayed, as well as the order inwhich they are displayed may be configurable by an operator of system10. In particular embodiments, email analyzer 20 may base aclassification of a relationship on factors other than emails betweentarget individual 80 and one or more persons in enterprise 15. Forexample, the classification may be based, at least in part, on emaildirectories and/or contact databases. Email analyzer 20 may be capableof receiving contact information from email server 30 and/or emailrepository 40. For example, email server 30 and/or email repository 40may store and/or maintain a contacts database used by contact managementsoftware. Contacts that are marked as “Knows Well” may be given higherpriority in the display of relationship information. In someembodiments, email analyzer 20 may identify and de-prioritize spamemails and/or may mask certain data (e.g., employee names, employeeidentification numbers, passwords, etc.) depending on the securityclearance of the user. Thus, email analyzer 20 may provide anintelligent display of relationships based on email traffic and/or otherinformation sources. Once presented with an ordered and intelligentlydisplayed list of relationships, a user of system 10 may leverage therelationships for further business interactions.

The steps illustrated in FIG. 7 may be combined, modified, or deletedwhere appropriate, and additional steps may also be added to thoseshown. Additionally, the steps may be performed in any suitable orderwithout departing from the scope of the present disclosure.

Although the present disclosure has been described with severalembodiments, numerous changes, variations, alterations, transformations,and modifications may be suggested to one skilled in the art, and it isintended that the present disclosure encompass such changes, variations,alterations, transformations, and modifications as fall within the scopeof the appended claims.

1. A method, comprising: identifying, with a processor, one or morerelationships between a target individual and one or more persons basedat least in part on a plurality of emails, wherein the plurality ofemails comprises: one or more outbound emails, the one or more outboundemails comprising emails sent to the target individual from the one ormore persons; and one or more inbound emails, the one or more inboundemails comprising emails sent from the target individual to the one ormore persons; for each of the one or more relationships, calculating anamount of outbound emails; for each of the one or more relationships,calculating an amount of inbound emails; assigning, with the processor,a classification to each of the one or more relationships based at leastin part on the amount of outbound emails and the amount of inboundemails; sorting, with the processor, the one or more relationships basedat least in part on the classification assigned to each of the one ormore relationships; and storing information regarding the sortedrelationships.
 2. The method of claim 1, further comprising displayingon a graphical user interface the one or more sorted relationships. 3.The method of claim 1, wherein the classification comprises at least oneof strong, moderate, and weak.
 4. The method of claim 1, furthercomprising: configuring a first threshold for the amount of outboundemails; and configuring a second threshold for the amount of inboundemails.
 5. The method of claim 4, wherein the classification of arelationship is based at least in part upon the amount of outboundemails in comparison to the first threshold.
 6. The method of claim 4,wherein the classification of a relationship is based at least in partupon the amount of inbound emails in comparison to the second threshold.7. The method of claim 1, wherein sorting the relationships is furtherbased upon priority rules.
 8. An apparatus, comprising: a processoroperable to: identify one or more relationships between a targetindividual and one or more persons based at least in part on a pluralityof emails, wherein the plurality of emails comprises: one or moreoutbound emails, the one or more outbound emails comprising emails sentto the target individual from the one or more persons; and one or moreinbound emails, the one or more inbound emails comprising emails sentfrom the target individual to the one or more persons; for each of theone or more relationships, calculate an amount of outbound emails; foreach of the one or more relationships, calculate an amount of inboundemails; assign a classification to each of the one or more relationshipsbased at least in part on the amount of outbound emails and the amountof inbound emails; and sort the one or more relationships based at leastin part on the classification assigned to each of the one or morerelationships; and a memory coupled to the processor and operable tostore information regarding the sorted relationships.
 9. The apparatusof claim 8, wherein the processor is further operable to display on agraphical user interface the one or more sorted relationships.
 10. Theapparatus of claim 8, wherein the classification comprises at least oneof strong, moderate, and weak.
 11. The apparatus of claim 8, wherein theprocessor is further operable to: configure a first threshold for theamount of outbound emails; and configure a second threshold for theamount of inbound emails.
 12. The apparatus of claim 11, wherein theclassification of a relationship is based at least in part upon theamount of outbound emails in comparison to the first threshold.
 13. Theapparatus of claim 11, wherein the classification of a relationship isbased at least in part upon the amount of inbound emails in comparisonto the second threshold.
 14. The apparatus of claim 8, wherein sortingthe relationships is further based upon priority rules.
 15. Software forprocessing emails, the software being embodied in a computer-readablemedium and when executed operable to: identifying one or morerelationships between a target individual and one or more persons basedat least in part on a plurality of emails, wherein the plurality ofemails comprises: one or more outbound emails, the one or more outboundemails comprising emails sent to the target individual from the one ormore persons; and one or more inbound emails, the one or more inboundemails comprising emails sent from the target individual to the one ormore persons; for each of the one or more relationships, calculating anamount of outbound emails; for each of the one or more relationships,calculating an amount of inbound emails; assigning a classification toeach of the one or more relationships based at least in part on theamount of outbound emails and the amount of inbound emails; sorting theone or more relationships based at least in part on the classificationassigned to each of the one or more relationships; and storinginformation regarding the sorted relationships.
 16. The software ofclaim 15, further comprising displaying the one or more sortedrelationships.
 17. The software of claim 15, wherein the classificationcomprises at least one of strong, moderate, and weak.
 18. The softwareof claim 15, further comprising: configuring a first threshold for theamount of outbound emails; and configuring a second threshold for theamount of inbound emails.
 19. The software of claim 18, wherein theclassification of a relationship is based at least in part upon theamount of outbound emails in comparison to the first threshold.
 20. Thesoftware of claim 18, wherein the classification of a relationship isbased at least in part upon the amount of inbound emails in comparisonto the second threshold.
 21. The software of claim 15, wherein sortingthe relationships is further based upon priority rules.
 22. A system forprocessing emails, comprising: an email repository operable to store rawemail data comprising outbound emails sent to a target individual from aparticular person and inbound emails sent from the target individual tothe particular person; an email analyzer communicatively coupled to theemail repository and operable to: identify one or more relationshipsbetween the target individual and the particular person based at leastin part upon a calculated amount of the outbound emails and a calculatedamount of the inbound emails; assign a classification to each of the oneor more relationships based at least in part on the calculated amount ofthe outbound emails and the calculated amount of the inbound emails;sort the one or more relationships based at least in part on theclassification assigned to each of the one or more relationships; andstore the sorted relationships.
 23. The system of claim 22, wherein theemail analyzer is further operable to display on a graphical userinterface the one or more sorted relationships.
 24. The system of claim22, wherein the classification comprises at least one of strong,moderate, and weak.
 25. The system of claim 22, wherein the emailanalyzer is further operable to: configure a first threshold for theamount of outbound emails; and configure a second threshold for theamount of inbound emails.
 26. The system of claim 25, wherein theclassification of a relationship is based at least in part upon theamount of outbound emails in comparison to the first threshold.
 27. Thesystem of claim 25, wherein the classification of a relationship isbased at least in part upon the amount of inbound emails in comparisonto the second threshold.
 28. The system of claim 25, wherein sorting therelationships is further based upon priority rules.